Don’t double-count extended GSM characters if text message is not GSM encoded #1371
Merged
Conversation
Characters like `{` only count as two characters if the message is
GSM-encoded.
If characters like Ŵ have caused the message to not be GSM-encoded then
`{` counts as 1 character like any other.
This bug existed before https://github.com/alphagov/notifications-utils/pull/1362/files
but wasn’t spotted. It’s quite unlikely to make a real-life difference
to billing given how infrequently these characters are used in messages.
Only 2 is the special case because that’s where the previous fragment varies in length. The maths in the general case works for 1-fragment messages
joybytes
approved these changes
Jun 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Characters like
{only count as 2 characters if the message is GSM-encoded.If characters like
Ŵhave caused the message to be unicode-encoded then{counts as 1 character like any other.This bug existed before #1362 but wasn’t spotted. It’s quite unlikely to make a real-life difference to billing given how infrequently these characters are used in messages.